🎨 Palette: Add empty state for new players#248
Conversation
Added an encouraging empty state message ("None yet! Go set a record!")
for the highscore display when it is 0. This clarifies the system state
for new users instead of confusingly hiding the UI element completely.
Also appended the corresponding UX learning to the internal journal.
Co-authored-by: EiJackGH <172181576+EiJackGH@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
💡 What:
Added an explicit, encouraging empty state for the "Personal Best" highscore display in the CLI game. Instead of hiding the section when the high score is 0, it now shows: "Personal Best: None yet! Go set a record!".
🎯 Why:
Hiding UI elements when data is empty creates an ambiguous and potentially confusing experience for new users onboarding into the application. Providing clear, encouraging empty states clarifies the system state and gives the user a call to action.
📸 Before/After:
Before:
After:
♿ Accessibility:
Improves cognitive accessibility by clearly conveying the state of the system ("you have no high score yet") rather than leaving it to the user's assumption through omission.
PR created automatically by Jules for task 15574569718411886942 started by @EiJackGH